Version 112 of the Linux Base Pack PowerPack updates the silo_apps library to version 5.4.0.
- Minimum Required SL1 Version: 12.1.1
Before You Install or Upgrade
Ensure that you are running version 12.1.1 or later of SL1 before installing "Linux Base Pack" PowerPack version 112.
For details on upgrading SL1, see the relevant SL1 Platform Release Notes.
You should check the thresholds for zombie processes and load average. The load average is compared to the threshold based on the normalized data per CPU.
Installing or Upgrading the PowerPack
If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.
To install this PowerPack:
- Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
- In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
- Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
- Click PowerPack file from step 1. and navigate to the
- Select the PowerPack file and click . The PowerPack Installer modal displays a list of the PowerPack contents.
- Click PowerPack is added to the PowerPack Manager page. . The
By default, installing a new version of a PowerPack will overwrite all content in that PowerPack that has already been installed on the target system. You can use the Enable Selective PowerPack Field Protection setting in the Behavior Settings page (System > Settings > Behavior) to prevent the new version of the PowerPack from overwriting local changes for some commonly customized fields.
For more information about using the PowerPack, see the Monitoring Linux manual.
Features
This release includes the following features:
- Dynamic Applications that discover and collect configuration and performance data for Linux systems
- Internal Collection Dynamic Applications that collect inventory and performance data for Linux systems
- Event Policies and corresponding alerts that are triggered when Linux systems meet certain status criteria
- Device Classes for each type of Linux system monitored
- A Run Book Action and an Automation policy to assign the proper device classes to Linux systems
Many of the Event Policies included in this PowerPack are disabled by default. You must manually enable the Event Policies that you want to use. To do so, go to the Event Policy Editor page (Registry > Events > Event Manager > create or edit) and change the Operational State to Enabled.
Enhancements and Issues Addressed
The following enhancements and addressed issues are included this release of the "Linux Base Pack":
- The version of silo_apps library was updated to 5.4.0. and the Execution Environment was renamed to "Linux Base Pack Environment 1.12".
- Addressed an issue in which an error in the Execution Environment in the Linux Base Pack PowerPack version 111 affected the discovery of Linux devices in SL1 version 12.1.1.
Known Issues and Workarounds
The following known issues affect version 112 of the Linux Base Pack PowerPack:
- A platform issue may affect Linux devices using a PEM key in the SSH credential after upgrading to SL1 versions prior to 12.2.4. If your Linux devices with a PEM key stop collecting data after upgrading, go to the SSH credential used by the affected devices and click to resolve the issue.
- If the Linux server that the PowerPack monitors, reports CLI-SSH with empty message ScienceLogic suggests checking the device since this is likely a timeout issue of the end device.
- Version 22.04 of Ubuntu and earlier may have problems discovering devices with a PEM key. It is recommended that you use a password in this case.
- Parsing may fail with some commands if there are custom images on the device.
- If you use the default timeout in the "Linux Example Credential" credential and continue to experience timeout and login errors on a limited number of servers, create a copy of the credential, and edit the timeout value to 10 seconds then align your new credential to the servers with login errors.
- Modifying any of the IC Dynamic Applications will change the value of the Collector Affinity setting from Assigned collector to Default. If you make any changes to the configuration of these Dynamic Applications, run the following query on the Database Tool (System > Tools > DB Tool):
SELECT ppguid FROM master.powerpack WHERE name = "Linux Base Pack"
Save the result of ppguid as <LBP PPguid>
UPDATE master.dynamic_app SET cu_affinity="2" WHERE ppguid = <LBP PPguid>
- CSR 1000v Series Cisco routers discovered after version 102 of the PowerPack should not be aligned with Linux Base Pack Dynamic Applications. After upgrading to version 103, Linux Base Pack Dynamic Applications aligned to the Cisco routers should be removed and the device class should be updated to the expected device class of the router.
- If you have a device with more than one SSH credential aligned, only one credential will be used. The connection to that credential will be maintained until it is terminated by the target host or the network, which means that it will continue to use the old credential through that connection even when the credential has changed.
- To discover Linux devices, the PowerPack uses an API call to align Dynamic Applications from the PowerPack to the devices. The API call length can cause API queries to back up and time out when attempting to discover multiple devices. As a workaround, ScienceLogic recommends leveraging SQL queries to align these Dynamic Applications.
- A collection exception appears in the device log if a device's hostname is not properly set.